chore(ci): Correct cron schedule comments in GitHub workflows #15222
Conversation
The comments for the scheduled cron jobs in the GitHub Actions workflows were inaccurate. Many referenced PST instead of the correct PDT during daylight saving time, and some of the hour conversions were incorrect. This change updates all cron schedule comments to accurately reflect their run times in both PDT and EDT, ensuring developers have a clear understanding of when these automated jobs will execute.
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. |
ncooke3
requested review from
paulb777 and
andrewheard
and removed request for
paulb777 and
andrewheard
The comments for the scheduled cron jobs in the GitHub Actions workflows were inaccurate. Many referenced PST instead of the correct PDT during daylight saving time, and some of the hour conversions were incorrect.
This change updates all cron schedule comments to accurately reflect their run times in both PDT and EDT, ensuring developers have a clear understanding of when these automated jobs will execute.